Shareware Grab Bag

home *** CD-ROM | disk | FTP | other *** search

/ Shareware Grab Bag / Shareware Grab Bag.iso / 081 / oevent4d.arc / OEVENT.DOC next >

Wrap

Text File | 1988-02-25 | 12.4 KB | 283 lines

OPUS <non-TM> EVENT muncher Version 4d February 25, 1988 One of the things about the continued growth of OPUS is that it con- stantly needs new utilities to maintain it. Hopefully this program will fill one of the needs for the people who are using OPUS 1.00 with its extended scheduling commands. OEVENT should be fairly simple to use, just type in: OEVENT [FILENAME.EXT] [-C] [-L [> PRN:] [>FILE.EXT] ] If no file is specified OEVENT will look for SCHED.BBS. The '-C' option will Create a new schedule file for OPUS with one ex- ternal event at midnight, for one minute, and keep the schedule in memory for editting. You do need one external event with OPUS each day. Just "OEVENT -C" will create SCHED.BBS, ready to edit. The '-L' option will List the events in the file specified, or if no file is specified, in SCHED.BBS. The screen will look like this: ------------------------------------------------------------------ Event Tag Day Start End Run? Exit Mail LO CM SX MO FR <5> <6> <7> <8> <9> <9> 0 Y ALL 9:00 22:00 ENA 5 1 * X ALL 1:01 1:02 ENA F 30 2 X ALL 3:30 3:35 ENA F 50 3 Z ALL 1:10 2:00 ENA Y N Y Y Y N 4 Z ALL 3:35 7:59 ENA Y N Y N N Y 5 X ALL 7:59 8:00 ENA F 59 6 Z ALL 8:00 23:01 ENA Y Y N N N Y 7 X ALL 5:30 5:30 DIS F 60 8 Z ALL 23:01 24:00 ENA Y N Y N N Y <-> Previous Event <+> Next Event <Q> Quit <H> Home <S> Start Time <E> End Time <F> Forced Event <I> Insert <R> Error Level <D> Day-of-week <T> Event Tag <O> Sort <*> Edit Everything <Z> Edit Behavior <G> Use GMT <L> Flush/Edit <1> Enable Event <2> Disable Event <3> Delete Event <N> Jump to N By your command? The Commands: --- --------- Most commands can be reached two or three ways. This is primarily to make sure that OEVENT will run on anything that OPUS will run on, but also means that you can pick any command set that you are comfortable with. "-", "_", Move Up Move to lower-number event, up on the screen. (Up Arrow on IBM and compatibles will also work) "+", "=" Move Down Move to higher-number event, down on the screen. (Down Arrow will also work on IBM and close compatibles) "<", ",", PgUp Page Up Moves up 8 Events, one screen full. ">", ".", PgDn Page Down Move down 8 Events, one screen full. H, Home Move to Event #0. Q Quit, Save the changes and exit. ESC Abort Abort this run. Do NOT save any of the changes. S Start Time Set the time that this event will start in Hour:Min, 24-hour format. E End Time Set the End of this event in Hour:Minute format. Must be equal to or less than Start Time, OPUS will _NOT_ carry an event past midnight. 0 Length events are possible by setting Start and End Times to the same value. (Handy for forced External Events) F Forced Event Make this a Forced Event. OPUS will run this event as soon as possible if some- thing creates a situation where the event is missed. (i.e. A user does a big upload just before the event, mail pac- ket is being transferred, etc.) I Insert Insert an event here. Will move all the events below it down and will DELETE the final event! Use with care if! R Error Level Set the Error Level for External Events or the length of time the bell will ring for Y)ell event. D Day-of-Week Set the Day of Week that this event runs. (0=Sunday, 1=Monday, ... 7=All) T Event Tag Change the Event Tag. A-W = External event with Errorlevel set to decimal value of uppercase letter. X = External Event, Errorlevel set by R command above. YOU MUST HAVE AT LEAST ONE EXTERNAL EVENT EVERY DAY FOR OPUS! Y = Yell Event. When do you want users to be able to get your attention. Should always be Event #0. Z = Behavior Event. Controls the way OPUS will handle mail, do Scans, and take care of the Outbound directory. O Sort Events Sorts events by Start Time. Should help you keep straight what is going on. Automatically packs events (gets rid of the Deleted Events mixed in with Dis- abled and Enabled Events). Does NOT sort Event 0 (the Y)ell event) or the Deleted Events. * Edit Everything Go through all the commands for an- event, automatically sets Event as En- abled. Z Edit Behavior Modify the way OPUS will handle outbound mail. Will give you a new Menu with specific commands. You can also alter the way OPUS will handle outbound mail during this event from the main menu, shown above, by using the numeric (or Function Keys on IBM compatibles) as listed here: 5, F1 Toggle Send Mail during this event. 6, F2 Toggle Local Mail Only, for those boards that are a no-charge call. 7, F3 Toggle Continuous-Mail only. Send only mail marked as "Crash" to another board that can accept mail 24 hours. 8, F4 Toggle Suppress Exits. If Yes, OPUS will NOT Exit when Crash-Mail or other reasons con- trolled by CTL file. 9, F5 Toggle Mail-Only. If Yes, will not accept human callers. 0, F6 Toggle File-Requests. If Yes, File-Requests will be honored. If No, will refuse them. G GMT Toggle using Greenwich Mean Time for this Event. P Pack Gets rid of Deleted Events in the middle of your schedule. Moves them down and pushes all the Enabled and Disabled Events up. N Jump N Jump to even N. 1 Enable Turn this Event on. 2 Disable Turn this Event off, but retain the information. 3 Delete Turn this Event off, and/or delete the informa- tion. Primary use is that it cleans up the dis- play. L Flush Flush what's been done to disk and continue edit- ing. V Done? Toggles the event flag that stores whether or not an event has been completed. If the event has been done, there will be an asterisk '*' on that line, if there is no asterisk, the event is still wait- ing to be done or doesn't run today. The event that OEVENT will operate on will be in inverse video. You can use either the cursor keys or the '+' and '-' keys to move up and down through the events. OEVENT also know about PgUp, PgDn and Home for quicker movement around the events. When you get to an event you wish to change you can choose the ap- propriate commands. For example '1', '2' or '3' changes an event from Enabled to Disabled to Deleted, or if you wish to change the behavior of OPUS as far as handling mail in an event that is already set to handle mail just use the 'Z' command. 'E' will edit everything about an event except for its enabled status. OEVENT is all menu-driven. I could never remember all the things I wanted to change in one pass, and OPUS crams so much more information into SCHED.BBS that it just isn't feasible to alter events from the command line. One subtle advantage is that OEVENT does allow zero-length events. That can be extremely helpful for doing special things like changing outbound message packets from Hold to Crash with OMMM.EXE. OPUS will allow them and will honor them, but the internal Event editor won't allow zero length events, at least as of XX9X. Please forward any comments/suggestions/bug-reports to: Doug Boone 119/5 August 10, 1987: (Oevent 4a) Added the ESC command to allow you to exit without saving any changes. ^C should also have the same effect. OEVENT opens the SCHED.BBS file, it reads the SCHED.BBS file, and it closes the SCHED.BBS file before it does anything else. This should be failsafe because what you are doing in memory does not affect what is stored on the disk until you Q)uit. Also worked on the problem of OEVENT getting upset with people who accidently hit letters when entering time values by reading in each character as it is typed and checking it. Moved the display of the time to where you'd expect it to be while its being typed in. One odd effect of this change is the way partial times are entered, for example if you enter, "1:1", OEVENT will assume you are trying to enter 1:01, and not 1:10. Hitting a carriage return in answer to a question should not scroll the screen up any more. It is a valid response for the Start and End time commands, telling OEVENT that you don't what to change that event after all. Most other commands will now just ignore invalid responses. August 22, 1987: (Oevent 4b) Fixed errors induced in OEVENT4A dealing with End of events. August 29, 1987: (Oevent 4c) Added the 'N' command to jump to a certain event, flag handling for SCAN ALL event (Not installed in OPUS yet!), and fixed Behavior Menu. February 11, 1988: (Oevent 4d) Removed the Scan All, Opus 1.0X will never have a Scan event and Opus 1.1X will use a different event structure. Added <L> Flush to disk command, the <V> done flag, and cleaned up the menus and display some- what.